Audit log enhancement

ABSTRACT

A system for monitoring actual access to data elements in an enterprise computer network and providing associated data, the system including an at least near real time data element audit subsystem providing audit output data including at least one of a time stamp, identification of an accessor, user depository stored data regarding the accessor, accessed data element data, affected data element data, type of access operation, source IP address of access and access outcome data, in at least near real time, relating to actual access to data elements in the enterprise computer network, and an additional data providing subsystem receiving in at least near real time at least a part of the audit output data and utilizing the at least part of the audit output data for providing additional data which is not part of the audit output data.

REFERENCE TO RELATED APPLICATIONS

Reference is hereby made to U.S. Provisional Patent Application62/344,634, entitled AUDIT LOG ENRICHMENT, filed Jun. 2, 2016, thedisclosure of which is hereby incorporated by reference and priority ofwhich is hereby claimed pursuant to 37 CFR 1.78(a)(4) and (5)(i).

Reference is also made to the following US patents and patentapplications, owned by the assignee, the disclosures of which are herebyincorporated by reference:

U.S. Pat. Nos. 7,555,482; 7,606,801; 8,561,146; 8,239,925; 8,438,611;8,438,612; 8,601,592; 8,578,507; 8,805,884; 8,533,787; 8,909,673;9,147,180; and

U.S. Published Patent Application Nos. 2009/0265780; 2011/0010758;2011/0061093; 2011/0296490; and 2012/0271853.

FIELD OF THE INVENTION

The present invention relates generally to audit logging and morespecifically to monitoring of actual access to data elements in anenterprise computer network.

BACKGROUND OF THE INVENTION

Various types of audit log systems are known in the art.

SUMMARY OF THE INVENTION

The present invention seeks to provide improved systems and methodsrelating to monitoring of actual access to data elements in anenterprise computer network and providing corresponding notificationsthereof, where relevant.

There is thus provided in accordance with a preferred embodiment of thepresent invention a system for monitoring actual access to data elementsin an enterprise computer network and providing associated data, thesystem including an at least near real time data element audit subsystemproviding audit output data including at least one of a time stamp,identification of an accessor, user depository stored data regarding theaccessor, accessed data element data, affected data element data, typeof access operation, source IP address of access and access outcomedata, in at least near real time, relating to actual access to dataelements in the enterprise computer network, and an additional dataproviding subsystem receiving in at least near real time at least a partof the audit output data and utilizing the at least part of the auditoutput data for providing additional data which is not part of the auditoutput data.

Preferably, the additional data providing subsystem provides theadditional data from at least one data source within the enterprisecomputer network.

Additionally or alternatively, the additional data providing subsystemprovides the additional data from at least one data source outside ofthe enterprise computer network.

Preferably, the additional data providing subsystem automaticallyprovides the additional data from at least one data source in responseto the audit output data received from the at least near real time dataelement audit subsystem.

Preferably, the additional data providing subsystem automaticallysearches the enterprise computer network in order to find data sourcesuseful to the additional data providing subsystem.

There is further provided in accordance with another preferredembodiment of the present invention a method for monitoring actualaccess to data elements in an enterprise computer network and providingassociated data, the method including providing in at least near realtime audit output data including at least one of a time stamp,identification of an accessor, user depository stored data regarding theaccessor, accessed data element data, affected data element data, typeof access operation, source IP address of access and access outcomedata, in at least near real time, relating to actual access to dataelements in the enterprise computer network and receiving at least partof the audit output data and utilizing the at least part of the auditoutput data for providing data which is not part of the audit outputdata.

Preferably, the additional data is received from at least one datasource within the enterprise computer network.

Additionally or alternatively, the additional data is received from atleast one data source outside of the enterprise computer network.

Preferably, the receiving and the utilizing occur automatically in atleast near real time.

Preferably, the method also includes automatically searching theenterprise computer network in order to find useful data sources.

There is additionally provided in accordance with another preferredembodiment of the present invention a system for monitoring actualaccess to data elements in an enterprise computer network and providingassociated data, the system including a data element audit subsystemproviding audit data including at least data relating to time stamps ofat least two actual accesses and IP addresses of computers used for thetwo actual accesses, an additional data providing subsystem receiving atleast a part of the audit data and utilizing the at least part of theaudit data for providing physical location data corresponding to the IPaddresses of the computers used for the two actual accesses and a timeand distance analysis engine indicating whether a time differencebetween the time stamps and a geographical separation between thephysical locations of the at least two actual accesses may feasiblycorrespond one to another, in view of a minimum time duration requiredto physically travel between the physical locations of the at least twoactual accesses.

Preferably, the data element audit subsystem provides the audit data inat least near real time.’

Preferably, the additional data providing subsystem provides thephysical location data in at least near real time.

Preferably, the time and distance analysis engine provides an indicationof whether the time difference between the time stamps and thegeographical separation between the physical locations of the at leasttwo actual accesses may feasibly correspond one to another in at leastnear real time.

Preferably, the additional data providing subsystem provides data fromat least one data source outside of the enterprise computer network.

There is furthermore provided in accordance with an additional preferredembodiment of the present invention a method for monitoring actualaccess to data elements in an enterprise computer network and providingassociated data, the method including providing audit data including atleast data relating to time stamps of at least two actual accesses andIP addresses of computers used for the two actual accesses, receiving atleast a part of the audit data and utilizing the at least part of theaudit data for providing physical location data corresponding to the IPaddresses of the computers used for the two actual accesses andindicating whether a time difference between the time stamps and ageographical separation between the physical locations of the at leasttwo actual accesses may feasibly correspond one to another in view of aminimum time duration required to physically travel between the physicallocations of the at least two actual accesses.

Preferably, the audit data is provided in at least near real time.

Preferably, the audit data is provided from at least one data sourceoutside of the enterprise computer network.

Preferably, the additional data is provided from at least one datasource outside of the enterprise computer network.

Preferably, the indication of whether a time difference between the timestamps and a geographical separation between the physical locations ofthe at least two actual accesses may feasibly correspond to each otheris provided in at least near real time.

There is also provided in accordance with another preferred embodimentof the present invention a system for monitoring actual access to dataelements in an enterprise computer network and providing associateddata, the system including an at least near real time data element auditsubsystem providing at least data relating to an individual performingat least one actual access and an additional data providing subsystemproviding to the data element audit subsystem, social network data froma social network, relating to activity of the individual on the socialnetwork.

Preferably, the additional data providing subsystem provides the socialnetwork data in at least near real time.

Preferably, the system also includes a time window calculation subsystemconfigured to indicate whether the activity on the social networkoccurred within a predetermined time window.

Preferably, the additional data providing subsystem automaticallyprovides the social network data in response to the data received fromthe data element audit subsystem.

Preferably, operation of the additional data providing subsystem istriggered by at least one occurrence of the activity on the socialnetwork of the individual.

Additionally or alternatively, operation of the additional dataproviding subsystem is triggered on a scheduled basis to analyzeoccurrence of activity on the social network of the individual.

Alternatively, operation of the additional data providing subsystem iscontinuously triggered to analyze ongoing activity on the social networkof the individual.

Additionally or alternatively, operation of the additional dataproviding subsystem is triggered by at least one user-defined rule whichis based at least on time and on occurrence of the activity.

Preferably, an output of the time window calculation subsystem triggersa retroactive analysis of past actual accesses to at least one dataelement in the enterprise computer network.

There is further provided in accordance with yet another preferredembodiment of the present invention a method for monitoring actualaccess to data elements in an enterprise computer network and providingassociated data, the method including providing in at least near realtime at least data relating to an individual performing at least oneactual access and receiving at least part of the data relating to theindividual performing at least one actual access and utilizing the partof the data relating to the individual performing at least one actualaccess for providing data from a social network, relating to activity onthe social network by the individual.

Preferably, the method also includes providing an indication of whetherthe activity on the social network was done within a predetermined timewindow.

Preferably, the data from the social network is provided automaticallyin response to the receiving the data relating to the individualperforming at least one actual access.

Additionally or alternatively, the providing data from the socialnetwork is triggered by at least one existence of predetermined activityon the social network by the individual.

Additionally or alternatively, the providing data from the socialnetwork occurs on at least a scheduled basis to analyze existence ofpredetermined activity on the social network by the individual.

Alternatively, the providing data from the social network occurscontinuously to analyze ongoing activity on the social network by theindividual.

Additionally or alternatively, the providing data from the socialnetwork occurs in accordance with at least one user-defined rule basedat least on time and on existence of predetermined activity on thesocial network by the individual.

Preferably, the indication of whether the activity on the social networkby the individual was done within a predetermined time window triggers aretroactive analysis of past actual accesses to at least one dataelement in the enterprise computer network.

There is also provided in accordance with another preferred embodimentof the present invention a system for monitoring actual access to dataelements in an enterprise computer network and providing associateddata, the system including an at least near real time data element auditsubsystem providing at least data relating to a frequency of actualaccess of an individual to at least one data element, an additional dataproviding subsystem for providing social network data indicatingexistence of a predetermined activity of the individual on at least onesocial network and a frequency analysis correlation engine receivingoutputs from the at least near real time data element audit subsystemand from the additional data providing subsystem and providingcorrelation data indicating the existence or non-existence of arelationship between timing of a change in the frequency of actualaccess and timing of the predetermined activity of the individual.

Preferably, the additional data providing subsystem provides the socialnetwork data in at least near real time.

Preferably, the frequency analysis correlation engine provides thecorrelation data indicating existence or non-existence of a relationshipbetween timing of a change in the frequency of actual access and timingof the predetermined activity, in at least near real time.

There is additionally provided in accordance with another preferredembodiment of the present invention a method for monitoring actualaccess to data elements in an enterprise computer network and providingassociated data, the method including providing in at least near realtime at least data relating to a frequency of actual access of anindividual to at least one data element, providing social network dataindicating existence of a predetermined activity of the individual on atleast one the social network and providing in at least near real timecorrelation data indicating existence or non-existence of a relationshipbetween timing of a change in the frequency of actual access and timingof the predetermined activity of the individual.

There is furthermore provided in accordance with a further preferredembodiment of the present invention a system for monitoring actualaccess to data elements in an enterprise computer network and providingassociated data, the system including an at least near real time dataelement audit subsystem providing at least data relating to an IPaddress of a computer used in at least one actual access to at least onedata element, performed by an individual, an additional data providingsubsystem for providing data indicating a malicious reputation of atleast one IP address and an analysis engine receiving outputs from theat least near real time data element audit subsystem and from theadditional data providing subsystem and providing data indicating thatthe IP address used in the at least one actual access performed by theindividual has a malicious reputation.

Preferably, the additional data providing subsystem provides the dataindicating a malicious reputation of at least one IP address, in atleast near real time.

Preferably, the additional data providing subsystem provides dataindicating a malicious reputation of at least one IP address, from atleast one data source outside of the enterprise computer network.

Preferably, the analysis engine provides the data indicating that the IPaddress used in the at least one actual access performed by theindividual has a malicious reputation in at least near real time.

Preferably, operation of the additional data providing subsystem istriggered by at least one existing actual access to at least one dataelement in the enterprise computer network.

Additionally or alternatively, operation of the additional dataproviding subsystem is triggered on a scheduled basis to analyze actualaccesses to at least one data element in the enterprise computernetwork.

Additionally or alternatively, operation of the additional dataproviding subsystem is triggered by at least one user defined rule,which is based at least on time and on the existence of the actualaccess.

Preferably, a notification from an external source triggers operation ofthe analysis engine to provide a retroactive analysis of past actualaccesses to at least one data element in the enterprise computernetwork.

Preferably, the notification triggers scrutiny of future actual accessesto at least one data element in the enterprise computer network.

There is also provided in accordance with still a further preferredembodiment of the present invention a method for monitoring actualaccess to data elements in an enterprise computer network and providingassociated data, the method including providing in at least near realtime at least data relating to an IP address of a computer used in atleast one actual access performed by an individual, providing in atleast near real time data indicating a malicious reputation of at leastone IP address and providing in at least near real time data indicatingthat the IP address used in the at least one actual access performed bythe individual has a malicious reputation.

Preferably, the data indicating a malicious reputation of at least oneIP address used in the at least one actual access performed by theindividual is provided from at least one data source outside of theenterprise computer network.

Preferably, at least one existing actual access to a data element in theenterprise computer network triggers the providing of the data relatingto an IP address of a computer used in at least one actual access.

Preferably, data is provided on a scheduled basis to analyze actualaccesses to at least one data element in the enterprise computernetwork.

Additionally or alternatively, the data is provided in accordance withat least one of user defined rule, which is based at least on time andon existence of the actual access.

Preferably, a notification from an external source triggers providing aretroactive analysis of past actual accesses to at least one dataelement in the enterprise computer network.

Preferably, the notification triggers scrutiny of future actual accessesto at least one data element in the enterprise computer network.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will be understood and appreciated more fullybased on the following detailed description taken in conjunction withthe drawings in which:

FIGS. 1A and 1B are simplified partially pictorial, partially blockdiagram illustrations of a system for monitoring access to data elementsin a computer network, showing first and second access scenariosrespectively, constructed and operative in accordance with a preferredembodiment of the present invention;

FIGS. 2A and 2B are simplified partially pictorial, partially blockdiagram illustrations of a system for monitoring access to data elementsin a computer network, showing first and second access scenariosrespectively, constructed and operative in accordance with anotherpreferred embodiment of the present invention;

FIGS. 3A and 3B are simplified partially pictorial, partially blockdiagram illustrations of a system for monitoring access to data elementsin a computer network, in first and second access scenariosrespectively, constructed and operative in accordance with a furtherpreferred embodiment of the present invention;

FIGS. 4A and 4B are simplified partially pictorial, partially blockdiagram illustrations of a system for monitoring access to data elementsin a computer network, in first and second access scenariosrespectively, constructed and operative in accordance with still anotherpreferred embodiment of the present invention; and

FIGS. 5A and 5B are simplified partially pictorial, partially blockdiagram illustrations of a system for monitoring access to data elementsin a computer network, in first and second access scenariosrespectively, constructed and operative in accordance with yet anotherpreferred embodiment of the present invention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Reference is now made to FIGS. 1A and 1B, which are simplified partiallypictorial, partially block diagram illustrations of a system formonitoring access to data elements in a computer network, in first andsecond access scenarios respectively, constructed and operative inaccordance with a preferred embodiment of the present invention.

As seen in FIGS. 1A and 1B, a user 100, legitimate in the case of FIG.1A and illegitimate in the case of FIG. 1B, has recently logged into anenterprise computer network, here designated by reference numeral 102.

In the cases illustrated in FIGS. 1A and 1B, log-in data for the givenlog-in event by user 100 is preferably continuously captured by a DataElement Audit Subsystem 104, which Data Element Audit Subsystem 104 ispreferably connected to the enterprise computer network 102.

Data Element Audit Subsystem 104 preferably provides audit output datain at least near real time relating to actual access to data elements inenterprise computer network 102. The audit output data may include atleast one of a time stamp, identification of an accessor, userdepository stored data regarding the accessor, accessed data elementdata, affected data element data, type of access operation, source IPaddress of access and access outcome data in at least near real time,relating to actual access to data elements in enterprise computernetwork 102. In this example at least the following log-in data ispreferably captured by Data Element Audit Subsystem 104: USER NAME, IPADDRESS OF COMPUTER USED FOR LOG-IN.

In accordance with a preferred embodiment of the present invention, theData Element Audit Subsystem 104 preferably transmits at least a part ofthe audit output data captured thereby to an Additional Data ProvidingSubsystem 106. Here, by way of example, the Data Element Audit Subsystem104 preferably transmits a USER NAME-based query to Additional DataProviding Subsystem 106.

Additional Data Providing Subsystem 106 in turn preferably utilizes atleast part of the audit output data received from Data Element AuditSubsystem 104 for providing additional data which is not part of theaudit output data. Additional Data Providing Subsystem 106 preferablyreceives the output data from Data Element Audit Subsystem 104 andutilizes the output data in at least near real time. The additional dataprovided by Additional Data Providing Subsystem 106 may be automaticallyprovided in response to the audit output received from the Data ElementAudit Subsystem 104. Additional Data Providing Subsystem 106 mayautomatically search enterprise computer network 102 in order to finddata sources useful thereto.

Here, by way of example, Additional Data Providing Subsystem 106preferably communicates with a database, such as a human resourcesdatabase 108 within the enterprise computer network 102 to retrieve username-based data, such as the physical home address of the user, asrecorded in the human resources database 108.

Additionally or alternatively, the USER NAME-based query may be sent bythe Additional Data Providing Subsystem 106 to other databases, such asdatabases within or outside the enterprise computer network, toascertain other physical addresses which are known to be legitimatelyassociated with the USER NAME.

Further in accordance with a preferred embodiment of the presentinvention, the Data Element Audit Subsystem 104 preferably transmits anIP ADDRESS OF COMPUTER USED FOR LOG-IN-based query to the AdditionalData Providing Subsystem 106. Additional Data Providing Subsystem 106 inturn communicates with a database, such as an external commerciallyavailable GEO/IP database 110, in order to retrieve IP ADDRESS OFCOMPUTER USED FOR LOG-IN-based data, such as the physical addressassociated with the IP address of the computer used for log-in.

Additionally in accordance with a preferred embodiment of the presentinvention, the results of the USER NAME-based query and of the IPADDRESS OF COMPUTER USED FOR LOG-IN-based query are supplied back to theAdditional Data Providing Subsystem 106. The Additional Data ProvidingSubsystem 106 preferably checks to see if the physical addressassociated with the IP address of the computer used for log-in matcheseither the physical home address corresponding to the user name or anyother physical addresses which are known to be legitimately associatedwith the user name.

Once the checking has been completed, the Additional Data ProvidingSubsystem 106 preferably supplies the results of the USER NAME-basedquery and the results of the IP ADDRESS OF COMPUTER USED FORLOG-IN-based query, as well as the results of the check that wasperformed, back to the Data Element Audit Subsystem 104.

In a scenario where the log-in is legitimate, such as in the caseillustrated in FIG. 1A, an audit data summary 120 may be supplied by theData Element Audit Subsystem 104 to an IT manager 122 of enterprisecomputer network 102, as needed.

In the example shown in FIG. 1A, where the user 100 is logging in fromhis home, the Data Element Audit Subsystem 104. preferably provides aLEGIT LOG-IN output indication, as seen in FIG. 1A in summary window 120in the fields: “Known Address?: YES” and “Status: OK”.

In a case where the log-in is illegitimate, as in FIG. 1B, automaticprotective measures, such as an immediate real time or near real timealert to an IT security manager may be provided. Specifically, the DataElement Audit Subsystem 104 may send the IT Manager 122 an alert 124including the reason for the alert, possible scenarios as to the cause,suggested action items, and a link to view the summary of the audit dataof the log-in event 120.

In the example shown in FIG. 1B, where the user is logging in from alocation not known to be legitimately associated with the USER NAME,such as Beijing China, a SUSPECT LOG-IN output indication is provided,as seen in FIG. 1B in the “Summary for IT Manager” 120 window in thefields: “Known Address?: NO” and “Status: ALERT”.

It is understood that Data Element Audit Subsystem 104, in combinationwith Additional Data Providing Subsystem 106, preferably forms a system130 for monitoring actual access to data elements in an enterprisecomputer network and providing associated data, which system 130preferably operates in at least near real time.

Reference is now made to FIGS. 2A and 2B, which are simplified partiallypictorial, partially block diagram illustrations of a system formonitoring access to data elements in a computer network, showing firstand second access scenarios respectively, constructed and operative inaccordance with another preferred embodiment of the present invention.

As seen in FIGS. 2A and 2B, a user 200, legitimate in the case of FIG.2A and illegitimate in the case of FIG. 2B, is logging into anenterprise computer network, here designated by a reference numeral 202.

In the cases illustrated in FIGS. 2A and 2B, audit data for the givenlog-in event by user 200 is preferably continuously captured by a DataElement Audit Subsystem 204 which is preferably connected to theenterprise computer network 202. In this example at least the followinglog-in data is preferably captured: USER NAME, IP ADDRESS OF COMPUTERUSED FOR LOG IN, LOG-IN TIMESTAMP, LAST LOG-OUT TIMESTAMP and LASTLOG-IN LOCATION. Log-in data for a given log-in event is preferablyprovided by Data Element Audit Subsystem 204 in at least near real time.

In accordance with a preferred embodiment of the present invention, theData Element Audit Subsystem 204 preferably transmits an IP ADDRESS OFCOMPUTER USED FOR LOG-IN-based query to an Additional Data ProvidingSubsystem 206. Additional Data Providing Subsystem 206 in turncommunicates with a database, such as an external commercially availableGEO/IP database 210, in order to retrieveIP-address-of-the-computer-used-for-log-in-based-data, such as thephysical address associated with the IP address of the computer used forlog-in.

Preferably the results of the IP ADDRESS OF COMPUTER USED FORLOG-IN-based query are supplied by the external GEO/IP database 210 tothe Additional Data Providing Subsystem 206.

Further in accordance with a preferred embodiment of the presentinvention, the Data Element Audit Subsystem 204 preferably supplies LASTLOG-OUT TIMESTAMP and LAST LOG-IN LOCATION to a Time and DistanceAnalysis Engine 212. Time and Distance Analysis Engine 212 is preferablyalso supplied with the results of the IP ADDRESS OF COMPUTER USED FORLOG IN-based query from the Additional Data Providing Subsystem 206.Preferably, the Additional Data Providing Subsystem 206 provides theresults of the IP ADDRESS OF COMPUTER USED FOR LOG IN-based query,including the physical address associated with the IP address of thecomputer used for log-in, in at least near real time.

Preferably, the Time and Distance Analysis Engine 212 supplies theresults of the IP ADDRESS OF COMPUTER USED FOR LOG IN-based query, suchas the physical address associated with the IP address of the computerused for log-in, as well as the LAST LOG-IN LOCATION, to an ExternalTravel Time Calculator 214.

Time and Distance Analysis Engine 212 preferably retrieves from ExternalTravel Time Calculator 214 an indication of the minimum time required totravel between the two locations, namely between the location associatedthe present log-in and the last log-in location. An external Travel TimeCalculator 214 suitable for use in embodiments of the present inventionmay be of a type commercially available from GOOGLE® GOOGLE MAPS®,WAZE®, MAPQUEST®, in order to retrieve an indication of the minimumtravel time between two locations.

Based on the retrieved time data from the External Travel TimeCalculator 214, the LAST LOG-OUT TIMESTAMP and the current LOG-INTIMESTAMP, the Time and Distance Analysis Engine 212 preferablycalculates and indicates whether it is realistic for user 200 to havetravelled from the previous log-in location to the location indicated bythe IP ADDRESS OF COMPUTER USED FOR LOG-IN-based query, within the timeduration indicated by the difference between the timestamp of the lastlog-out and the timestamp captured in the present log-in event. Time andDistance Analysis Engine 212 preferably provides an indication ofwhether it is realistic for user 200 to have travelled from the previousto the present log-in location in at least near real time.

In the example shown in FIG. 2A, the Time and Distance Analysis Engine212 provides an analysis result to the Data Element Audit Subsystem 204indicating that it is realistic for the user to have travelled thedistance between the two geographical locations within the time durationindicated by the difference in log-out/log-in timestamps.

The Data Element Audit Subsystem 204 then supplies a warningnotification 220 to an IT Manager 222, which warning notification 220preferably includes at least a statement of the cause of the warning,possible explanations of that cause, suggested actions to be taken bythe IT Manager and a link to view a summary 224 of audit data of the login event. As seen in the SUMMARY FOR IT MANAGER window 224, particularlysignificant fields include: KNOWN ADDRESS?: NO, IS DISTANCE FROM LASTLOGIN FEASIBLE?: YES.

The warning notification 220 may be supplied in response to a request bythe IT manager 222 from the Data Element Audit Subsystem 204, or may beincluded in a periodically scheduled summary report including similarlog-in events within a specified timeframe.

In the example shown in FIG. 2B, the Time and Distance Analysis Engine212 provides an analysis result to the Data Element Audit Subsystem 204indicating that it is not realistic for the user to have travelled thedistance between the two locations within the time duration indicated bythe difference in log-out/log-in timestamps.

The Data Element Audit Subsystem 204 then supplies an alert notification226 to IT Manager 222, which alert notification 226 preferably includesat least a statement of the cause of the alert, possible explanationsfor that cause, the reason why the alert was triggered and a link toview the summary 224 of audit data of the log-in event. As seen in theSUMMARY FOR IT MANAGER window 224, particularly significant fieldsinclude: KNOWN ADDRESS?: NO, IS DISTANCE FROM LAST LOGIN FEASIBLE?: NO

In both of the cases of FIGS. 2A and 2B, automatic protective measures,such as an immediate real time or near real time notification to an ITsecurity manager are preferably provided.

It is understood that Data Element Audit Subsystem 204, in combinationwith Additional Data Providing Subsystem 206 and Time and DistanceAnalysis Engine 212, preferably form a system 230 for monitoring actualaccess to data elements in an enterprise computer network and forproviding associated data, which system 230 preferably operates in atleast near real time.

Reference is now made to FIGS. 3A and 3B, which are simplified partiallypictorial, partially block diagram illustrations of a system formonitoring access to data elements in a computer network, in first andsecond access scenarios respectively, constructed and operative inaccordance with a further preferred embodiment of the present invention.

In accordance with a preferred embodiment of the present invention, aTriggering Subsystem 300 connected to an enterprise computer network 302is preferably used to trigger a process of providing data, preferablymetadata, from a social media network and ascertaining on the basisthereof, whether a given enterprise user of enterprise computer network302 has updated his/her social media network profile. It is appreciatedthat Triggering Subsystem 300 may form a part of system 130, illustratedin FIGS. 1A and 1B.

The Triggering Subsystem 300 preferably triggers the process byproviding a triggering output to an Additional Data Providing Subsystem304. The Triggering Subsystem 300 may be configured to trigger operationof Additional Data Providing Subsystem 304 based on detection ofpredetermined activity on a social network of the enterprise user, or inresponse to a manual request by an administrator. Triggering Subsystem300 may additionally or alternatively be configured to trigger operationof Additional Data Providing Subsystem 304 in accordance with at leastone user-defined rule, which rule may be based at least on time anddetection of predetermined activity on the social network.

Additionally or alternatively, Triggering Subsystem 300 may triggeroperation of Additional Data Providing Subsystem 304 periodicallyaccording to a predetermined schedule, in order to analyze theoccurrence of predetermined activity on the social network of anenterprise user. Alternatively, Triggering Subsystem 300 may beconfigured to trigger the process continuously, in order to continuouslyanalyze ongoing activity of enterprise users on the social network.

Responsive to the triggering output, the Additional Data ProvidingSubsystem 304 requests an enterprise user repository 306 to provide anenterprise user name corresponding to a given enterprise user.

The enterprise user repository 306 preferably maintains a list of useridentifications, states, roles, group memberships, and passwords. Theuser repository 306 may be realized as an ACTIVE DIRECTORY® service,available from Microsoft Corporation, Redmond, Wash., USA. The userrepository 306 is a logical unit that may be preferably distributed overone or more enterprise servers, e.g., a domain controller. In additionto storing user data, the user repository 306 preferably facilitatesassignment of enterprise-wide policies, deployment of programs andapplication of critical updates to the entire organization. By way ofexample, an enterprise user repository suitable for use in embodimentsof the present invention may be of the type described in U.S. Pat. No.8,881,232, incorporated herein by reference.

Upon receipt by the Additional Data Providing Subsystem 304 of theenterprise user name from the enterprise user repository 306, theAdditional Data Providing Subsystem 304 preferably communicates withresources external to the enterprise computer network, such as anexternal Social Database 308, and receives from these resources themetadata associated with social media network profile updates performedby the identified enterprise user. Preferably, the metadata includes atimestamp corresponding to an update made by the enterprise user tohis/her profile, as seen at metadata timestamp fields 310.

Upon receiving from the external Social Database 308, a timestampcorresponding to an update, the Additional Data Providing Subsystem 304may ascertain whether the update on the enterprise user's social medianetwork account profile occurred within a predetermined range of time.Additional Data Providing Subsystem 304 may ascertain whether the updateon the enterprise user's social media network account profile occurredwithin a predetermined range of time by providing the timestampcorresponding to an update to a Time Window Calculation Subsystem 312.

Updates which are found by Time Window Calculation Subsystem 312 to haveoccurred earlier than the predetermined range of time may be discardedor may be provided to a Data Element Audit Subsystem 314 for potentialfuture audit purposes, as see in FIG. 3A. A record of such updates maybe made available in the form of reports deliverable either upon requestor on a scheduled basis. Additional Data Providing Subsystem 304preferably provides the social network data to the Data Element AuditSubsystem 314 in at least near real time.

The Data Element Audit Subsystem 314 preferably stores data relating toenterprise users who have performed actual access within the enterprisecomputer network 300. Particularly, Data Element Audit Subsystempreferably provides data in at least near real time relating to anindividual performing at least one actual access. Additional DataProviding Subsystem 304 may provide the social network data to the DataElement Audit Subsystem 314 in response to data received from the DataElement Audit Subsystem 314.

Optionally, upon an update having been found to have occurred outside ofthe predetermined range of time, the Additional Data Providing Subsystem304 may trigger a Notification Subsystem 316.

As seen in FIG. 3A, the timestamp 310 provided by the External SocialNetwork Database 308 shows that the enterprise user last updated his/hersocial media network profile on “2012-01-07-10:37:43”. This timestamp isearlier than the predetermined time range, typically set to be one monthprior to the date of notification.

In this case, an enterprise IT Manager 322 preferably receives a summaryreport 324 of an enterprise employee's social network account profileupdate status, stating that no recent updates have been made to theemployee's social network account. The report may be provided eitherupon request, or on a scheduled basis.

Updates which are found by Time Window Calculation Subsystem 312 to haveoccurred within the predetermined range of time are preferablycommunicated by the Additional Data Providing Subsystem 304 to the DataElement Audit Subsystem 314 for potential future audit purposes, as seenin FIG. 3B. Additional Data Providing Subsystem 304 preferably providesthe social network data to the Data Element Audit Subsystem 314 in atleast near real time.

Upon an update having been found to have occurred within thepredetermined range of time, Additional Data Providing Subsystem 304preferably also triggers Notification Subsystem 316.

Upon an update having been found to have occurred within thepredetermined range of time, the Notification Subsystem 316 isconfigured, responsive to a trigger from the Additional Data ProvidingSubsystem 304, to notify enterprise IT Manager 322 that a user hasrecently updated his/her social network profile. The notification may bein the form of an email, text message, pop-up notification on a remotecomputer used by the IT manager and connected to the enterprise computernetwork 302 or any other means of communication, various types of whichare well known in the art.

As seen in FIG. 3B, the timestamp provided by the External SocialNetwork Database 308, shows that the user last updated his/her socialmedia network profile on “2016-01-07-10:37:43”, which timestamp lieswithin the predetermined range of time of interest.

Updating of a social network account profile such as LINKEDIN® mayindicate that an employee is planning on resigning from his/her positionat the enterprise and is therefore editing their social media accountprofiles, such as LINKEDIN®, in order to attract potential newemployers.

The enterprise IT Manager 322 receives an alert 326, in real time or innear real time. The alert preferably indicates that an enterprise userhas recently updated his/her LINKEDIN® social network profile, may bepotentially considering leaving the enterprise and therefore that actionitems should preferably be taken by the IT Manager.

Upon an update having been found to have occurred within thepredetermined range of time, Time Window Calculation Subsystem 312 maytrigger a retroactive analysis of past actual accesses by the enterpriseuser to at least one data element in enterprise computer network 302.

It is understood that Triggering Subsystem 300, Data Element AuditSubsystem 314, in combination at least with Additional Data ProvidingSubsystem 304 and Notification Subsystem 316, preferably form a system330 for monitoring actual access to data elements in an enterprisecomputer network and for providing associated data, which system 330preferably operates in at least near real time.

Reference is now made to FIGS. 4A and 4B, which are simplified partiallypictorial, partially block diagram illustrations of a system formonitoring access to data elements in a computer network, in first andsecond access scenarios respectively, constructed and operative inaccordance with still another preferred embodiment of the presentinvention.

FIG. 4A illustrates a scenario in which an enterprise IT manager issuspicious that an employee may be considering leaving the enterprise.The enterprise IT Manager therefore implements a review of theemployee's recent activity on the enterprise computer network andgenerates a report thereof. In the scenario of FIG. 4A, the generatedreport shows the enterprise employee's recent activity as beinganomalous, in terms of actual access to enterprise data elements. Thereport also indicates that no recent changes in social network accounts,profiles and/or status updates have been made. Such a report may beprovided upon request of an administrator or on a scheduled basis.

FIG. 4B illustrates a similar scenario, in which in addition to thereport showing anomalous behavior by an employee in terms of actualaccess to enterprise data elements, the report also indicates that therehave been recent updates to the employee's LINKEDIN® social networkprofile. In this case, the enterprise IT Manager may receive an alert,in real time or in near real time, indicative of these findings.

Anomalous behavior may be considered to be behavior that isuncharacteristic or unusual such as, but not limited to, actual accessto data elements that have previously not been accessed by the employee,an increase or decrease in the number or frequency of actual accesses todata elements or absence of actual access to data elements. A thresholdof anomalous behavior may be predetermined by the enterpriseadministration. A threshold may be, by way of example only, a change of25% in the number or frequency of actual accesses compared to a typicalor average number or frequency of actual accesses.

Updating a social network profile such as LINKEDIN® may indicate thatthe employee is planning on resigning from his/her position at theenterprise. Social network status updates associated with, ormentioning, the enterprise may indicate that the employee isdissatisfied with his/her current work environment. Relevant statusupdates may be detected using a predefined set of rules and/ordictionaries including keywords, which keywords may be predefined by theenterprise administration.

Turning now to FIGS. 4A and 4B, an enterprise computer network 402 maybe connected to a Data Element Audit Subsystem 404. Data Element AuditSubsystem 404 preferably operates both as a data recorder and as ananalysis engine.

As a data recorder, the Data Element Audit Subsystem 404 preferablyrecords data relating to actual access events by enterprise employees,including attempted accesses which were successful as well as attemptedunsuccessful accesses.

As an analysis engine, the Data Element Audit Subsystem 404 preferablydevelops a measure of similarity among users in their relationships todata elements, based on granted permissions and patterns of actualaccess. Particularly, Data Element Audit Subsystem 404 preferablyprovides, in at least near real time, data relating to a frequency ofactual access of an enterprise user to at least one data element.

When anomalous behavior, such as a sudden increase in the frequency ofactual accesses of an employee, is detected, the Data Element AuditSubsystem 404 preferably initiates a process of providing data,preferably metadata, from a social media network and ascertaining on thebasis thereof, whether a given enterprise employee has updated his/hersocial media network profile and/or status.

The Data Element Audit Subsystem 404 preferably provides an initiatingoutput, including the enterprise employee's name, to an Additional DataProviding Subsystem 406.

The Additional Data Providing Subsystem 406 preferably communicates withresources external to the enterprise computer network 402, such asexternal social databases 408. Additional Data Providing Subsystem 406preferably receives from these resources metadata associated with socialmedia network profile and/or status updates performed by the enterpriseemployee, indicating the existence of a predetermined activity by theenterprise employee on at least one social network. Additional DataProviding Subsystem 406 preferably operates in at least near real timeto provide the social network data associated with the user's activityon the social network.

Upon receiving metadata from external social databases 408, preferablyincluding a timestamp corresponding to an update, the Additional DataProviding Subsystem 406 preferably ascertains whether the update on theenterprise user's social media network account status matches thepredefined set of rules and/or dictionaries. Status updates not matchingrules of keywords are discarded. The Additional Data Providing Subsystem406 additionally preferably ascertains whether the update on theenterprise user's social media network account profile, and/or theremaining status updates, occurred within a predetermined range of time.

Particularly preferably, Additional Data Providing Subsystem 406preferably provides the social network data indicating a user's activityon the social network to a frequency analysis correlation engine 409.Frequency analysis correlation engine 409 preferably also receives fromData Element Audit Subsystem 404 data relating to changes in frequencyof actual access by the user to data elements. Frequency analysiscorrelation engine 409 is preferably operative to provide correlationdata indicating the existence or non-existence of a relationship betweentiming of a change in said frequency of actual access and the timing ofsaid predetermined activity of said individual. Such correlation data ispreferably provided by frequency analysis correlation engine 409 in atleast near real time.

Social media updates which are found to have occurred earlier than apredetermined range of time, such that, for example, no correlation isfound between the timing of the social media updates and timing ofchanges in frequency of actual access to data elements, may be discardedor provided to Data Element Audit Subsystem 404 for potential futureaudit purposes, as seen in FIG. 4A. Such reports may be delivered eitherupon request, or on a scheduled basis.

Optionally, upon an update having been found to have occurred outside ofthe predetermined range of time, the Additional Data Providing Subsystem406 may trigger a Notification Subsystem 410. The Notification Subsystem410 is preferably configured to notify an enterprise IT Manager 422 thatan enterprise user had a recent change in number or frequency of actualaccesses to enterprise data elements but did not recently update his/hersocial network profile and/or status. The notification may be in theform of a summary report 424 delivered as an email, text message, orpop-up notification on a remote computer used by the IT manager.

Social media updates which are found to have occurred within thepredetermined range of time, such that, for example, a correlation isfound to exist between the timing of the social media updates and timingof changes in frequency of actual access to data elements, arepreferably communicated by the Additional Data Providing Subsystem 406to the Data Element Audit Subsystem 404 for potential future auditpurposes, as seen in FIG. 4B. Additionally, Additional Data ProvidingSubsystem 406 preferably activates Notification Subsystem 410.

The Notification Subsystem 410 is preferably configured to alertenterprise IT Manager 422 that an enterprise user, who has had a recentchange in number of actual accesses to enterprise data elements, hasalso recently updated his/her social network profile and/or status. Analert 426 may be delivered as an email, text message, or pop-upnotification on a remote computer used by the IT manager.

As seen in FIG. 4A, an enterprise user last updated his/her social medianetwork profile on “2012-01-07-10:37:43”, which timestamp is earlierthan the predetermined range of time of interest. In contrast, in FIG.4B, the enterprise user last updated his/her social media networkprofile on “2016-01-07-10:37:43” which timestamp is within thepredetermined range of time of interest. As a result, in the scenario ofFIG. 4A the IT Manager 422 may be provided with status summary report424 of recent anomalous enterprise user behavior, whereas in thescenario illustrated in FIG. 4B, the IT Manager 422 preferably receivesalert 426 preferably indicating that the enterprise user may beconsidering leaving the enterprise, and optionally also recommendingactions to be taken.

It is understood that Data Element Audit Subsystem 404, in combinationat least with Additional Data Providing Subsystem 406 and NotificationSubsystem 410, preferably form at least part of a system 430 formonitoring actual access to data elements in an enterprise computernetwork and for providing associated data, which system 430 preferablyoperates in at least near real time. System 430 preferably serves toprovide a clear picture of enterprise usage patterns, recommendationsfor security policy optimization, and alerts of anomalous user behavior.

Reference is now made to FIGS. 5A and 5B, which are simplified partiallypictorial, partially block diagram illustrations of a system formonitoring access to data elements in a computer network, in first andsecond access scenarios respectively, constructed and operative inaccordance with yet another preferred embodiment of the presentinvention.

FIGS. 5A and 5B illustrate a preferred embodiment of a system of thepresent invention, in the case that an enterprise IT manager isperforming a review of recent log-ins, such as log-ins by a user 500,from remote locations into an enterprise computer network 502. Thesystem of the present invention preferably generates a report ofarchived log-in event data. It is appreciated that such a report may begenerated periodically, upon demand or in response to a particularevent.

In the scenario illustrated in FIG. 5A, the generated report indicatesthat enterprise employee 500 has recently logged into the enterprisecomputer network from a remote location and that the IP address used inthe login event is legitimate and not identified as malicious.

In the scenario illustrated in FIG. 5B, the generated report indicatesthan an IP address used in a recent log-in event has been previouslyidentified and labelled as malicious. As a result, the system generatesa report and notifies the enterprise IT manager by way of an alertstating that there has been a log-in into the enterprise computernetwork from an illegitimate IP address. The enterprise IT manager mayoptionally proceed to expand the alert message and view a summary of theevent in the generated report.

Turning now to FIGS. 5A and 5B, a Data Element Audit Subsystem 504connected to the enterprise computer network 502 preferably continuouslycaptures log-in event data. By way of example, the Data Element AuditSubsystem 504 preferably captures at least an IP address of a computerused in a remote log-in event.

The Data Element Audit Subsystem 504 preferably transmits anIP-Address-Of-Computer-Used-For-Log-In-based-query to an Additional DataProviding Subsystem 506, which Additional Data Providing Subsystem 506in turn preferably communicates with an external, commercially availabledatabase 508.

The external database 508 preferably provides an output to theAdditional Data Providing Subsystem 506 stating whether the IP addresssupplied by the Additional Data Providing Subsystem 506 to the externaldatabase 508 has been previously designated as malicious.

An IP address may be identified and labelled as potentially maliciouswhen use of a device such as computer or mobile device having that IPaddress has been previously associated with malicious incidents orspamming activity. Commercially available online databases, such aswww.ipvoid.com, provide data regarding IP addresses that have beenpreviously labelled as malicious.

The Additional Data Providing Subsystem 506 preferably delivers the datareceived from the external database 508, to the Data Element AuditSubsystem 504, where the data is stored together with the existinglog-in event data. The Additional Data Providing Subsystem 506preferably provides the data in at least near real time.

It is appreciated that Additional Data Providing Subsystem 506 may betriggered to communicate with external database 508 to investigatestatus of an IP address on a scheduled basis, or in accordance with atleast one user-defined rule based at least on time and occurrence ofactual access to data elements by an enterprise user.

The Data Element Audit Subsystem preferably supplies the data concerningthe status of the identified IP address and the log-in event data to ananalysis engine 509.

In the embodiment of FIG. 5A, the data provided by the external database508 indicates that the IP address used for the log-in has not previouslybeen identified as malicious. Data Element Audit Subsystem 504 providesthe analysis engine 509 with the requested archived log-in data and theIP address status data. Analysis engine 509 triggers generation anddelivery to an IT manager 522, by a Notification Subsystem 510, of asummary report 524. As seen in FIG. 5A, the summary report 524 indicatesthat a remote log-in has occurred from a non-malicious IP address.

In the embodiment of FIG. 5B, the data provided by the external database508 indicates that the IP address used for log-in was previouslylabelled and identified as malicious. Once stored with the existingevent data, the Data Element Audit Subsystem 504 then provides theassociated event data to the analysis engine 509, which in turn triggersgeneration of an alert 526 by Notification Subsystem 510, which alert526 is preferably sent to the enterprise IT manager 522.

The Notification Subsystem 510 may be configured to notify the ITmanager by email, text message, pop up notification or other forms ofcommunication to a computer or mobile device, as are well known in theart.

In some cases, analysis engine 509 may be triggered by a notificationreceived from an external source to provide a retroactive analysis ofpast actual accesses to data elements in enterprise network 502. Such anotification may also trigger scrutiny of future accesses to at leastone data element in enterprise network 502.

It is understood that Data Element Audit Subsystem 504, in combinationat least with Additional Data Providing Subsystem 506 and NotificationSubsystem 510, preferably form at least part of a system 530 formonitoring actual access to data elements in an enterprise computernetwork and for providing associated data, which system 530 preferablyoperates in at least near real time.

It will be appreciated by persons skilled in the art that the presentinvention is not limited by what has been particularly claimedhereinbelow. Rather, the scope of the invention includes variouscombinations and subcombinations of the features described hereinaboveas well as modifications and variations thereof as would occur topersons skilled in the art upon reading the forgoing description withreference to the drawings and which are not in the prior art.

1-37. (canceled)
 38. A system for monitoring actual access to dataelements in an enterprise computer network and providing associateddata, the system comprising: an at least near real time data elementaudit subsystem providing at least data relating to a frequency ofactual access of an individual to at least one data element; anadditional data providing subsystem for providing social network dataindicating existence of a predetermined activity of said individual onat least one social network; and a frequency analysis correlation enginereceiving outputs from said at least near real time data element auditsubsystem and from said additional data providing subsystem andproviding correlation data indicating the existence or non-existence ofa relationship between timing of a change in said frequency of actualaccess and timing of said predetermined activity of said individual. 39.A system according to claim 38 and wherein said additional dataproviding subsystem provides said social network data in at least nearreal time.
 40. A system according to claim 38 and wherein said frequencyanalysis correlation engine provides said correlation data indicatingexistence or non-existence of a relationship between timing of a changein said frequency of actual access and timing of said predeterminedactivity, in at least near real time.
 41. A method for monitoring actualaccess to data elements in an enterprise computer network and providingassociated data, the method comprising: providing hi at least near realtime at least data relating to a frequency of actual access of anindividual to at least one data element; providing social network dataindicating existence of a predetermined activity of said individual onat least one said social network; and providing in at least near realtime correlation data indicating existence or non-existence of arelationship between timing of a change in said frequency of actualaccess and timing of said predetermined activity of said individual. 42.A system for monitoring actual access to data elements in an enterprisecomputer network and providing associated data, the system comprising:an at least near real time data element audit subsystem providing atleast data relating to an IP address of a computer used in at least oneactual access to at least one data element, performed by an individual;an additional data providing subsystem for providing data indicating amalicious reputation of at least one IP address; and an analysis enginereceiving outputs from said at least near real time data element auditsubsystem and from said additional data providing subsystem andproviding data indicating that said IP address used in said at least oneactual access performed by said individual has a malicious reputation.43. A system according to claim 42 and wherein said additional dataproviding subsystem provides said data indicating a malicious reputationof at least one IP address, in at least near real time.
 44. A systemaccording to claim 42 and wherein said additional data providingsubsystem provides data indicating a malicious reputation of at leastone IP address, from at least one data source outside of said enterprisecomputer network.
 45. A system according to claim 42 and wherein saidanalysis engine provides said data indicating that said IP address usedin said at least one actual access performed by said individual has amalicious reputation in at least near real time.
 46. A system accordingto claim 42 and wherein operation of said additional data providingsubsystem is triggered by at least one existing actual access to atleast one data element in said enterprise computer network.
 47. A systemaccording to claim 42 and wherein operation of said additional dataproviding subsystem is triggered on a scheduled basis to analyze actualaccesses to at least one data element in said enterprise computernetwork.
 48. A system according to claim 42 and wherein operation ofsaid additional data providing subsystem is triggered by at least oneuser defined rule, which is based at least on time and on said existenceof said actual access.
 49. A system according to claim 42 and wherein anotification from an external source triggers operation of said analysisengine to provide a retroactive analysis of past actual accesses to atleast one data element in said enterprise computer network.
 50. A systemaccording to claim 49 and wherein said notification triggers scrutiny offuture actual accesses to at least one data element in said enterprisecomputer network.
 51. A method for monitoring actual access to dataelements in an enterprise computer network and providing associateddata, the method comprising: providing in at least near real time atleast data relating to an IP address of a computer used in at least oneactual access performed by an individual; providing in at least nearreal time data indicating a malicious reputation of at least one IPaddress; and providing in at least near real time data indicating thatsaid IP address used in said at least one actual access performed bysaid individual has a malicious reputation.
 52. A method according toclaim 51 and wherein said data indicating a malicious reputation of atleast one IP address used in said at least one actual access performedby said individual is provided from at least one data source outside ofsaid enterprise computer network.
 53. A method according to claim 51 andwherein at least one existing actual access to a data element in saidenterprise computer network triggers said providing of said datarelating to an IP address of a computer used in at least one actualaccess.
 54. A method according to claim 51 and wherein said data isprovided on a scheduled basis to analyze actual accesses to at least onedata element in said enterprise computer network.
 55. A method accordingto claim 51 and wherein said data is provided in accordance with atleast one of user defined rule, which is based at least on time and onexistence of said actual access.
 56. A method according to claim 51 andwherein a notification from an external source triggers providing aretroactive analysis of past actual accesses to at least one dataelement in said enterprise computer network.
 57. A method according toclaim 56 and wherein said notification triggers scrutiny of futureactual accesses to at least one data element in said enterprise computernetwork.